Skip to content

[doc-only] pathfinder: clarify Windows DLL search semantics#1795

Open
rwgk wants to merge 1 commit intoNVIDIA:mainfrom
rwgk:pathfinder_win_path_doc_update
Open

[doc-only] pathfinder: clarify Windows DLL search semantics#1795
rwgk wants to merge 1 commit intoNVIDIA:mainfrom
rwgk:pathfinder_win_path_doc_update

Conversation

@rwgk
Copy link
Collaborator

@rwgk rwgk commented Mar 20, 2026

Fixes #1781

Document that Python 3.8+ excludes PATH from the native Windows DLL search used by cuda.pathfinder, so CTK installs are typically found via CUDA_HOME/CUDA_PATH or other explicit locations instead.

Made-with: Cursor

Document that Python 3.8+ excludes PATH from the native Windows DLL search used
by cuda.pathfinder, so CTK installs are typically found via CUDA_HOME/CUDA_PATH
or other explicit locations instead.

Made-with: Cursor
@rwgk rwgk changed the title docs(pathfinder): clarify Windows DLL search semantics [doc-only] pathfinder: clarify Windows DLL search semantics Mar 20, 2026
@rwgk rwgk requested review from cpcloud and mdboom March 20, 2026 00:26
@rwgk
Copy link
Collaborator Author

rwgk commented Mar 20, 2026

@cpcloud @mdboom Issue #1781 turned out to be a real rabbit hole, mainly because I started out with the wrong expectation (that PATH is meant to searched). See the comment here, and the comment right after:

I believe simply updating the documentation is best, but please let me know if you have a different opinion.

@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG][pathfinder] Windows system search fails to find any CUDA DLL when CUDA_HOME/CUDA_PATH are not set

2 participants